Method and apparatus for controlling selection of the solution for wlan and unlicensed spectrum usage

ABSTRACT

Embodiments of systems and methods relating to a cellular communications network and Wireless Local Area Network (WLAN) integration/aggregation are disclosed. In some embodiments, a method of operation of a Mobility Management Entity (MME) of a cellular communications network comprises obtaining subscription information for a User Equipment (UE). The subscription information includes one or more Allowed Wireless Local Area Network/Unlicensed Band Solution (AWUBS) indications that are indicative of one or more AWUBSs that are allowed for the UE. The method further comprises sending a UE context related request to a base station in a radio access network of the cellular communications network. The UE context related request includes one of the one or more AWUBS indications.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a divisional of U.S. patent application Ser.No. 14/930,189, filed on Nov. 2, 2015, the disclosure and content ofwhich is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to Third Generation Partnership Project(3GPP) and Wireless Local Area Network (WLAN)integration/aggregation/interworking.

BACKGROUND Third Generation Partnership Project (3GPP)/Wireless LocalArea Network (WLAN) Interworking

Most current Wi-Fi/WLAN deployments are totally separate from mobilenetworks and can be seen as non-integrated from the terminalperspective. Most Operating Systems (OSs) for User Equipment devices(UEs) such as Android™ and iOS® devices, support a simple Wi-Fioffloading mechanism where a UE immediately switches all its InternetProtocol (IP) traffic to a Wi-Fi network upon detection of a suitablenetwork with a received signal strength above a certain level. Notably,Wi-Fi and WLAN are herein used interchangeably. Henceforth, the decisionto offload to a Wi-Fi network or not is referred to as access selectionstrategy and the term “Wi-Fi-if-coverage” is used to refer to theaforementioned strategy of selecting a Wi-Fi network whenever such anetwork is detected.

There are several drawbacks of the “Wi-Fi-if-coverage” strategy. A firstdrawback is that, although the user/UE can save previous pass codes foralready accessed Wi-Fi Access Points (APs), hotspot login for previouslynon-accessed APs usually requires user intervention, either by enteringthe pass code in a Wi-Fi Connection Manager (CM) or using a webinterface. The CM is software on a UE that is in charge of managing thenetwork connections of the terminal, taking into account userpreferences, operator preferences, network conditions, etc.

A second drawback is that no consideration of expected user experienceis made except those considered in the UE implemented as a proprietarysolution, and this can lead to a UE being handed over from a high datarate mobile network connection to a low data rate Wi-Fi connection. Eventhough the UE's OS or some high level software is smart enough to makethe offload decisions only when a signal level on a Wi-Fi network isconsiderably better than a mobile network link, there can still belimitations on the backhaul of the Wi-Fi AP that may end up being abottleneck.

A third drawback is that no consideration of the load conditions in themobile network and the Wi-Fi network are made. As such, the UE mightstill be offloaded to a Wi-Fi AP that is serving several UEs while themobile network (e.g., Long Term Evolution (LTE)) that it was previouslyconnected to is rather unloaded.

A fourth drawback is that interruptions of on-going services can occurdue to the change of IP address when the UE switches to the Wi-Finetwork. For example, a user who started a Voice over IP (VoIP) callwhile connected to a mobile network is likely to experience a call dropwhen arriving home and the UE switching to the Wi-Fi networkautomatically. Though some applications are smart enough to handle thisand survive the IP address change (e.g., Spotify®), the majority ofcurrent applications do not. This places a burden on applicationdevelopers if they have to ensure service continuity.

A fifth drawback is that no consideration of the UE's mobility is made.Due to this, a fast moving UE can end up being offloaded to a Wi-Fi APfor a short duration, just to be handed over back to the mobile network.This is especially a problem in scenarios like restaurants and cafeswith open Wi-Fi network, where a user walking by or even driving by therestaurant or cafe might be affected. Such ping pong between Wi-Fi andmobile networks can cause service interruptions as well as generateconsiderable unnecessary signaling (e.g., towards authenticationservers).

Recently, Wi-Fi has been subject to increased interest from cellularnetwork operators, and not only as an extension to fixed broadbandaccess. The interest is mainly about using the Wi-Fi technology as anextension, or alternative, to cellular radio access network technologiesto handle the always increasing wireless bandwidth demands. Cellularoperators that are currently serving mobile users with, e.g., any of the3GPP technologies (LTE, Universal Mobile Telecommunications System(UMTS)/Wideband Code Division Multiple Access (WCDMA), or Global Systemfor Mobile Communications (GSM)) see Wi-Fi as a wireless technology thatcan provide good support in their regular cellular networks. The term“operator-controlled Wi-Fi” points to a Wi-Fi deployment that on somelevel is integrated with a cellular network operator's existing networkand where 3GPP radio access networks and Wi-Fi wireless access may evenbe connected to the same core network and provide the same services.

There is currently quite intense activity in the area ofoperator-controlled Wi-Fi in several standardization organizations. In3GPP, activities to connect Wi-Fi APs to the 3GPP-specified core networkis pursued, and in Wi-Fi Alliance (WFA), activities related tocertification of Wi-Fi products are undertaken, which to some extentalso is driven from the need to make Wi-Fi a viable wireless technologyfor cellular operators to support high bandwidth offerings in theirnetworks. The term “Wi-Fi offload” is commonly used and points towardscellular network operators seeking means to offload traffic from theircellular networks to Wi-Fi, e.g., in peak traffic hours and insituations when the cellular network for one reason or another needs tobe off-loaded, e.g., to provide requested quality of service, maximizebandwidth, or simply for coverage.

Radio Access Network (RAN) Level Integration in Release 12 (Rel-12)

3GPP has specified a feature/mechanism for WLAN/3GPP radio interworkingwhich improves operator control with respect to how a UE performs accessselection and traffic steering between 3GPP and WLANs belonging to theoperator or its partners. The mechanism may also be used for other,non-operator, WLANs as well, even though this is not the main target.

It is discussed that, for this mechanism, the RAN provides assistanceparameters that helps the UE in access selection. RAN assistanceinformation is composed of three main components; namely, thresholdvalues, an Offloading Preference Indicator (OPI), and WLAN identifiers.The UE is also provided with RAN rules/policies that make use of theseassistance parameters. The threshold values could be, for example, formetrics such as 3GPP signal related metrics, Reference Signal ReceivedPower (RSRP)/Reference Signal Received Quality (RSRQ)/Received SignalCode Power (RSCP)/Energy per Chip/spectral Noise density (Ec/No), WLANsignal related metrics such as Received Channel Power Indicator(RCPI)/Received Signal Strength Indication (RSSI), WLANload/utilization, WLAN backhaul load/capacity, etc. One example of a RANrule that uses the threshold value could be that the UE should connectto a WLAN if the RSRP is below the signaled RSRP threshold at the sametime as the WLAN RCPI is above the signaled RCPI threshold (it is alsodiscussed that the RAN should provide thresholds for when the UE shouldsteer traffic back from WLAN to 3GPP). The RAN rules/policies areexpected to be specified in a 3GPP specification such as TechnicalSpecification (TS) 36.304 V12.0.0 and/or TS 36.331 V12.1.0.

With the above mechanism, it is likely not wanted, or maybe not evenfeasible, that the UE considers any WLAN when deciding where to steertraffic. For example, it may not be feasible that the UE uses thismechanism to decide to steer traffic to a WLAN not belonging to theoperator. Hence, it has been proposed that the RAN should also indicateto the UE for which WLANs the mechanism should be applied by sendingWLAN identifiers.

The RAN may also provide additional parameters which are used in AccessNetwork Discovery and Selection Function (ANDSF) policies. One proposedparameter is OPI. One possibility for OPI is that it is compared to athreshold in the ANDSF policy to trigger different actions. Anotherpossibility is that OPI is used as a pointer to point to and selectdifferent parts of the ANDSF policy, which would then be used by the UE.

The RAN assistance parameters (i.e., thresholds, WLAN identifiers, OPI)provided by the RAN may be provided with dedicated signaling and/orbroadcast signaling. Dedicated parameters can only be sent to the UEwhen having a valid Radio Resource Control (RRC) connection to the 3GPPRAN. A UE which has received dedicated parameters applies dedicatedparameters; otherwise, the UE applies the broadcast parameters. If noRRC connection is established between the UE and the RAN, the UE cannotreceive dedicated parameters.

In 3GPP, it has been agreed that ANDSF should be enhanced for Rel-12 touse the thresholds and OPI parameters that are communicated by the RANto the UE. If enhanced ANDSF policies are provided to the UE, the UEwill use the ANDSF policies instead of the RAN rules/policies (i.e.,ANDSF has precedence).

Tight Integration/Aggregation between 3GPP and WLAN

Within the scope of 3GPP Release 13 (Rel-13), there has been a growinginterest in realizing even tighter integration/aggregation between 3GPPand WLAN (e.g., integration/aggregation in the same way as carrieraggregation between multiple carriers in 3GPP, where the WLAN is usedjust as another carrier). Such an aggregation is expected to make itpossible for a more optimal aggregation opportunity as compared toMultiPath Transmission Control Protocol (MPTCP), as the aggregation isperformed at a lower layer (e.g., at a lower protocol layer) and as suchthe scheduling and flow control of the data on the WLAN and 3GPP linkscan be controlled by considering dynamic radio network conditions.

FIGS. 1A through 1C illustrate three different protocol options fortight integration/aggregation between 3GPP and WLAN at the Packet DataConvergence Protocol (PDCP), Radio Link Control (RLC), and Medium AccessControl (MAC) levels, respectively. Note that otherintegration/aggregation schemes are also possible. For instance, oneother example is to perform the aggregation/integration above the PDCPprotocol layer. FIGS. 1A through 1C show the main principles forintegration/aggregation at the PDCP level, the RLC level, and the MAClevel, respectively, and additional functionality that may be needed.For example, in the PDCP level aggregation, an additional protocol layermay be used between the PDCP layer and the 802.2 Logical Link Control(LLC) layer to convey information about the UE and the radio bearer thetraffic is associated with (this additional protocol layer is shown as“Glue 1” in FIGS. 2A and 2B).

Note that FIGS. 1A through 1C show the protocol stack at a UE. In thecase of a standalone AP and enhanced or evolved Node B (eNB) (i.e., APand eNB are not co-located), the protocol stack for supportingaggregation is a little bit different, as the LLC frames now have to berelayed towards the standalone eNB. FIG. 2A illustrates this for thecase of PDCP level aggregation. In this case, once the LLC packet isdecoded at the AP (in the uplink direction from the UE to the AP) andthe AP realizes that this packet is a PDCP packet that has to be routedto an eNB, the forwarding can be performed, for example, via normalTransmission Control Protocol (TCP)/IP protocol stack. FIG. 2B showsPDCP level aggregation with a co-located/combined eNB and AP.

A study item entitled “Study on Multiple Radio Access Technology(Multi-RAT) joint coordination” has been finalized in 3GPP TSG RAN3 for3GPP Release 13 (see 3GPP Technical Report (TR) 37.870 Release 13). Thestudy item included investigation of potential enhancements of RANinterfaces and procedures to support the joint operation among differentRadio Access Technologies (RATs), including WLAN. For the 3GPP-WLANcoordination part, it was agreed to focus on non-integrated 3GPP/WLANnodes since integrated nodes are a matter of implementation. The studyrecommends the specification of an interface between Evolved UniversalTerrestrial Radio Access Network (EUTRAN) and WLAN, and an architectureincluding such an interface is shown in FIG. 3. The interface betweenthe WLAN AP and the eNB is referred to as an Xw interface from hereonwards.

When it comes to aggregation, the Xw interface can be used not only forforwarding the aggregated data, but also for control plane signalingregarding the aggregation. Note that for the case of co-located APs andeNBs, a proprietary interface could be employed for the provision ofsimilar functionalities.

The control plane protocol architecture between the UE and the eNB (forthe case of WLAN related control signaling) and also between the eNB andthe WLAN AP are illustrated in FIGS. 4 and 5. As shown in FIG. 4, theeNB can configure the settings of some of the UE's WLAN parameters andbehavior via RRC signaling. On the other hand, as shown in FIG. 5, theeNB uses the XwAP application protocol of the Xw interface to configurethe WLAN AP.

Carrier Aggregation (CA) and Licensed Assisted Access (LAA)

The LTE Release 10 (Rel-10) specifications have been standardized,supporting Component Carrier (CC) bandwidths up to 20 Megahertz (MHz)(which is the maximum LTE Release 8 (Rel-8) carrier bandwidth). An LTERel-10 operation wider than 20 MHz is possible and appears as a numberof LTE CCs to a LTE Rel-10 UE. The straightforward way to obtainbandwidths wider than 20 MHz is by means of CA. CA implies that an LTERel-10 UE can receive multiple CCs, where each CC has, or at least hasthe possibility to have, the same structure as a Rel-8 carrier. CA isillustrated in FIG. 6. The Rel-10 standard supports up to fiveaggregated CCs where each CC is limited in the Radio Frequency (RF)specifications to have a one of six bandwidths namely 6, 15, 25, 50, 75,or 100 Resource Blocks (RBs) (corresponding to 1.4, 3 5 10 15 and 20 MHzrespectively).

The number of aggregated CCs as well as the bandwidth of the individualCCs may be different for uplink and downlink. A symmetric configurationrefers to the case where the number of CCs in downlink and uplink is thesame whereas an asymmetric configuration refers to the case that thenumber of CCs is different in downlink and uplink. It is important tonote that the number of CCs configured in the network may be differentfrom the number of CCs seen by a UE. A UE may, for example, support moredownlink CCs than uplink CCs, even though the network offers the samenumber of uplink and downlink CCs.

CCs are also referred to as cells or serving cells. More specifically,in an LTE network, the cells aggregated by a UE are denoted PrimaryServing Cell (PCell) and Secondary Serving Cells (SCells). The term“serving cell” comprises both PCell and SCells. All UEs have one PCell.The cell that is a UE's PCell is UE specific and is considered “moreimportant,” i.e. vital control signaling and other important signalingis typically handled via the PCell. Uplink control signaling is alwayssent on a UE's PCell. The CC configured as the PCell is the Primary CC(PCC), whereas all other CCs are SCells. The UE can send and receivedata both on the PCell and the SCells. For control signaling such asscheduling commands, the control signaling can be configured to only betransmitted and received on the PCell but where the commands are alsovalid for the SCell, or the control signaling can be configured to betransmitted and received on both the PCell and the SCells. Regardless ofthe mode of operation, the UE will only need to read the broadcastchannel in order to acquire system information parameters on the PCC.System information related to the Secondary Component Carriers (SCCs)may be provided to the UE in dedicated RRC messages.

During initial access, a LTE Rel-10 UE behaves similar to a LTE Rel-8UE. However, upon successful connection to the network, a Rel-10 UEmay—depending on its own capabilities and the network—be configured withadditional serving cells in the uplink and downlink. Configuration isbased on RRC. Due to the heavy signaling and rather slow speed of RRCsignaling, it is envisioned that a UE may be configured with multipleserving cells even though not all of them are currently used.

Different deployment scenarios for CA in relation to frequency bands andthe placement of cells within frequency bands is shown in FIG. 7. Thedifferent variants are i) intra-band aggregation, contiguous cells, ii)intra-band aggregation, non-contiguous cells and iii) inter-bandaggregation. The different frequency bands are part of licensedspectrum.

To summarize, LTE CA supports efficient use of multiple carriers,allowing data to be sent/received over all carriers. There is supportfor cross-carrier scheduling avoiding the need for the UE to listen toall carrier-scheduling channels all the time. The solution relies ontight time synchronization between the carriers. The synchronizationrequirements impact the different deployment possibilities. It ispossible to both have Intra-Digital Unit (Intra-DU) CA meaning that thePCell and all the SCell(s) are controlled by the same DU. Inter-DU CA,on the other hand, means that the PCell and SCell(s) may be controlledby different DUs.

LAA generally relates to applying LTE CA to the unlicensed spectrum. Themain driver is the assumption of high availability of unlicensedspectrum globally and the use of this unlicensed spectrum for smallcells. Unlicensed spectrum is used as a performance booster managed by alicensed carrier in LTE LAA. In relation to the above description aboutLTE CA, it can be described that the PCell is always in the licensedspectrum and that the SCell may use unlicensed bands (in addition to orwithout SCell(s) on licensed bands). LAA is shown in FIG. 8 and is avariant of inter-band aggregation (as shown in FIG. 7). LAA is alsocalled LTE-LAA.

Subscriber Profile ID (SPID) for RAT/Frequency Priority

SPID is one mechanism for the core network to indicate UE-specificpreferences to RAN. It is currently used, for example, for both activeand idle mode mobility control of the UE.

SPID is assigned to specific subscriptions and stored in a HomeSubscriber Server (HSS), as illustrated in FIG. 9. FIG. 9 morespecifically illustrates SP ID handling in different nodes of thecellular network. SPID is also known as RAT/Frequency Selection Priority(RFSP) index. Therefore, the SPID stored in HSS is sometimes referred toas a Subscribed RFSP index. A default value is also possible. A MobilityManagement Entity (MME) receives the SPID from the HSS during the UEattach procedure and the SPID is also stored in the MME. At UE contextsetup, the MME forwards the SPID to the eNB, and the eNB prioritizes theRATs and carriers for both active and idle mode mobility based on theSPID. For roaming subscribers, the MME can remove or add an SPID basedon International Mobile Subscriber Identity (IMSI) analysis.

The SP ID value mapping in the eNB to a specific set of RATs/carriers(i.e., to be used as dedicated priority information towards the UE) areconfigurable as it may be operator strategy dependent. Some examples aregiven below in Table 1. Number 7 indicates highest priority and (No) is“forbidden.” For example, SPID value of 2 would indicate that the UE isnot allowed to access LTE, and that WCDMA has higher priority than GSM.

TABLE 1 SPID LTE C1 LTE C2 WCDMA GSM Subscription Default 7 6 5 4 Normal1 No No 6 7 Telephony only 2 No No 7 6 No LTE

There are different ways in which to send the SPID from the core networkto the RAN. In LTE, the relevant S1AP messages used to send the SPIDfrom the Evolved Packet Core (EPC) to the RAN are INITIAL CONTEXT SETUPREQUEST, UE CONTEXT MODIFICATION REQUEST, DOWNLINK Non-Access Stratum(NAS) TRANSPORT, and HANDOVER REQUEST. In addition, the SubscriberProfile Identity (SPID) for a RAT/frequency priority Information Element(IE) is also transferred between eNBs over the X2 interface at handover.

Handover Restriction List (HRL)

The HRL IE can be used to define roaming and access restrictions forsubsequent mobility actions for which the eNB provides information aboutthe target of the mobility action towards the UE, e.g., handover andcell change order, or for Secondary Cell Group (SCG) selection duringdual connectivity operation. The HLR can contain information aboutserving Public Land Mobile Network (PLMN), equivalent PLMNs, forbiddentracking areas, forbidden location areas, and forbidden inter-RATs.

There are different ways in how the HRL can be sent from the corenetwork to the RAN. In LTE, the relevant S1AP messages that can be usedto send the HRL from the EPC to the RAN are INITIAL CONTEXT SETUPREQUEST, DOWNLINK NAS TRANSPORT, and HANDOVER REQUEST.

SUMMARY

Embodiments of systems and methods relating to cellular communicationsnetwork and Wireless Local Area Network (WLAN) integration/aggregationare disclosed. In some embodiments, a method of operation of a basestation of a cellular communications network comprises obtaining one ormore Allowed WLAN/Unlicensed Band Solution (AWUBS) indications from acore network of the cellular communications network. The one or moreAWUBS indications are indicative of one or more AWUBSs allowed for aparticular User Equipment device (UE). The method further comprisesusing one of the one or more AWUBSs with respect to the UE. In thismanner, the base station is enabled to obtain an indication(s) of theAWUBS(s) allowed for the UE and then use only an allowed AWUBS for thatUE.

In some embodiments, the one or more AWUBS indications consist of asingle AWUBS indication that is indicative of a single AWUBS that isallowed for the UE. In other embodiments, the one or more AWUBSindications comprise multiple AWUBS indications that are indicative ofmultiple AWUBSs that are allowed for the UE.

In some embodiments, obtaining the one or more AWUBS indications fromthe core network comprises obtaining a list of AWUBS indications, wherean ordering of the one or more AWUBS indications within the list ofAWUBS indications is indicative of relative priorities of the one ormore AWUBS indications. Further, in some embodiments, the relativepriorities of the one or more AWUBS indications are UE specific. Inother embodiments, the relative priorities of the one or more AWUBSindications are universal for the cellular communications network. Inother embodiments, obtaining the one or more AWUBS indications from thecore network comprises obtaining a list of AWUBS indications withoutpriorities.

In some embodiments, the one or more AWUBS indications obtained from thecore network consist of multiple AWUBS indications, and the methodfurther comprises selecting a desired one of the one or more AWUBSsindicated by the one or more AWUBS indications to be used with respectto the UE. Using the desired one of the one or more AWUBSs comprisesusing the desired one of the one or more AWUBSs selected by the basestation. Further, in some embodiments, selecting the desired one of theone or more AWUBSs comprises selecting the desired one of the one ormore AWUBSs based on at least one of a group consisting of: capabilitiesof the UE, knowledge of one or more AWUBSs supported by the basestation, and knowledge of one or more AWUBSs supported by an associatedWLAN Access Point (AP).

In other embodiments, the one or more AWUBS indications comprisemultiple AWUBS indications indicative of multiple AWUBSs that areallowed for the UE. Obtaining the one or more AWUBS indications from thecore network comprises obtaining the AWUBS indications and indicationsof relative priorities of the AWUBSs indicated by the AWUBS indicationsfrom the core network, and selecting the desired one of the one or moreAWUBSs comprises selecting the desired one of the one or more AWUBSsbased on the relative priorities of the AWUBSs indicated by the AWUBSindications and at least one of a group consisting of: capabilities ofthe UE, knowledge of one or more AWUBSs supported by the base station,and knowledge of one or more AWUBSs supported by an associated WLAN AP.

In some embodiments, obtaining the one or more AWUBS indications fromthe core network comprises obtaining the one or more AWUBS indicationsfrom the core network when a UE context is created for the UE in a RadioAccess Network (RAN) of the cellular communications network. In otherembodiments, obtaining the one or more AWUBS indications from the corenetwork comprises obtaining the one or more AWUBS indications from thecore network when a UE context is modified for the UE in a RAN of thecellular communications network.

In some embodiments, the method further comprises receiving a requestfrom the UE to transition from idle state to connected state, sendingthe request to the core network, and, as a result of sending the requestto the core network, receiving, from the core network, the one or moreAWUBS indications.

In some embodiments, the method further comprises receiving a requestfrom the UE to transition from idle state to connected state, sendingthe request to the core network, and, as a result of sending the requestto the core network, receiving, from the core network, a UE contextrelated request comprising the one or more AWUBS indications.

In some embodiments, obtaining the one or more AWUBS indications fromthe core network comprises obtaining the one or more AWUBS indicationsfrom the core network using a Subscriber Profile Identity (SPID)Information Element associated with the UE. In other embodiments,obtaining the one or more AWUBS indications from the core networkcomprises obtaining the one or more AWUBS indications from the corenetwork using a Handover Restriction List (HRL) IE associated with theUE. In other embodiments, obtaining the one or more AWUBS indicationsfrom the core network comprises obtaining the one or more AWUBSindications from the core network using an IE associated with the UE.

In some embodiments, using the one of the one or more AWUBSs withrespect to the UE comprises sending one or more parameters to the UE. Inother embodiments, using the one of the one or more AWUBSs with respectto the UE comprises providing one of a group consisting of Packet DataConvergence Protocol (PDCP) level cellular network and WLAN integration,Radio Link Control (RLC) level Third Generation Partnership Project (3GPP) and WLAN integration, and Medium Access Control (MAC) level 3GPPand WLAN integration with respect to the UE. In other embodiments, usingthe one of the one or more AWUBSs with respect to the UE comprisesconfiguring a Secondary Component Carrier (SCC) for the UE in anunlicensed frequency spectrum according to a Licensed Assisted Access(LAA) scheme.

Embodiments of a base station of a cellular communications network arealso disclosed.

Embodiments of a method of operation of Mobility Management Entity (MME)of a cellular communications network are also disclosed. In someembodiments, the method of operation of the MME comprises obtainingsubscription information for a UE, wherein the subscription informationcomprises one or more AWUBS indications that are indicative of one ormore AWUBSs that are allowed for the UE. The method further comprisessending a UE context related request to a base station in a RAN of thecellular communications network, where the UE context related requestcomprises one of the one or more AWUBS indications.

In some embodiments, the one or more AWUBS indications consists of asingle AWUBS indication that is indicative of a single AWUBS that isallowed for the UE. In other embodiments, the one or more AWUBSindications comprises multiple AWUBS indications that are indicative ofmultiple AWUBSs that are allowed for the UE.

In some embodiments, the subscription information comprises a list ofAWUBS indications consisting of the one or more AWUBS indications, wherean ordering of the one or more AWUBS indications within the list ofAWUBS indications is indicative of relative priorities of the one ormore AWUBS indications. In some embodiments, the relative priorities ofthe one or more AWUBS indications are UE specific. In other embodiments,the relative priorities of the one or more AWUBS indications areuniversal for the cellular communications network. In other embodiments,the subscription information comprises a list of AWUBS indicationsconsisting of the one or more AWUBS indications without priorities.

In some embodiments, the UE context related request comprises a SP ID IEassociated with the UE that comprises the one or more AWUBS indications.In other embodiments, the UE context related request comprises a HRL IEassociated with the UE that comprises the one or more AWUBS indications.In other embodiments, the UE context related request comprises an IEassociated with the UE that comprises the one or more AWUBS indications.

Embodiments of a MME are also disclosed.

Embodiments of a method of operation of a Home Subscriber Server (HSS)of a cellular communications network are also disclosed. In someembodiments, the method of operation of the HSS comprises receiving arequest from a network node for subscription information for a UE and,in response, sending the subscription information for the UE to thenetwork node. The subscription information comprises one or more AWUBSindications that are indicative of one or more AWUBSs that are allowedfor the UE.

In some embodiments, the one or more AWUBS indications consists of asingle AWUBS indication that is indicative of a single AWUBS that isallowed for the UE. In other embodiments, the one or more AWUBSindications comprises multiple AWUBS indications that are indicative ofmultiple AWUBSs that are allowed for the UE.

In some embodiments, the subscription information comprises a list ofAWUBS indications consisting of the one or more AWUBS indications, wherean ordering of the one or more AWUBS indications within the list ofAWUBS indications is indicative of relative priorities of the one ormore AWUBS indications. In some embodiments, the relative priorities ofthe one or more AWUBS indications are UE specific. In other embodiments,the relative priorities of the one or more AWUBS indications areuniversal for the cellular communications network. In other embodiments,the subscription information comprises a list of AWUBS indicationsconsisting of the one or more AWUBS indications without priorities.

In some embodiments, sending the subscription information to the networknode comprises sending the subscription information such that thesubscription information comprises an IE comprising the one or moreAWUBS indications.

Embodiments of an HSS are also disclosed.

Those skilled in the art will appreciate the scope of the presentdisclosure and realize additional aspects thereof after reading thefollowing detailed description of the embodiments in association withthe accompanying drawing figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawing figures incorporated in and forming a part ofthis specification illustrate several aspects of the disclosure, andtogether with the description serve to explain the principles of thedisclosure.

FIGS. 1A through 1C illustrate three different protocol options fortight integration/aggregation between Third Generation PartnershipProject (3GPP) and a Wireless Local Area Network (WLAN) at the PacketData Convergence Protocol (PDCP), Radio Link Control (RLC), and MediumAccess Control (MAC) levels, respectively;

FIG. 2A illustrates relaying of Logical Link Control (LLC) framestowards a standalone base station for the case of PDCP levelaggregation;

FIG. 2B illustrates PDCP level aggregation with a co-located/combinedbase station and WLAN Access Point (AP);

FIG. 3 illustrates an architecture for 3GPP and WLANintegration/aggregation including an interface between the base stationand WLAN AP;

FIGS. 4 and 5 illustrate a control plane protocol architecture between aUser Equipment device (UE) and a base station and also between a basestation and the WLAN AP;

FIG. 6 illustrates Carrier Aggregation (CA);

FIG. 7 illustrates different deployment scenarios for CA;

FIG. 8 illustrates Licensed Assisted Access (LAA);

FIG. 9 illustrates Subscriber Profile Identity (SPID) handling indifferent nodes of the cellular network;

FIG. 10 illustrates a wireless system that enablesintegration/aggregation of a cellular network and a WLAN according tosome embodiments of the present disclosure;

FIGS. 11 through 15 illustrate the operation of the wireless system ofFIG. 10 according to various embodiments of the present disclosure;

FIGS. 16 and 17 are block diagrams of a base station according to someembodiments of the present disclosure;

FIG. 18 is a block diagram of a network node according to someembodiments of the present disclosure;

FIG. 19 is a block diagram of a Mobility Management Entity (MME)according to some embodiments of the present disclosure; and

FIG. 20 is a block diagram of a Home Location Register (HLR)/HomeSubscriber Server (HSS) according to some embodiments of the presentdisclosure.

DETAILED DESCRIPTION

The embodiments set forth below represent information to enable thoseskilled in the art to practice the embodiments and illustrate the bestmode of practicing the embodiments. Upon reading the followingdescription in light of the accompanying drawing figures, those skilledin the art will understand the concepts of the disclosure and willrecognize applications of these concepts not particularly addressedherein. It should be understood that these concepts and applicationsfall within the scope of the disclosure and the accompanying claims.

An interworking mechanism between Wireless Local Area Networks (WLANs)and Third Generation Partnership Project (3GPP) networks has beenstandardized in 3GPP Release 12 (Rel-12). However, only the concept ofinterworking between the two networks has been covered in 3GPP Rel-12(i.e., though data traffic from/to a given User Equipment device (UE)can either be provisioned via the WLAN or 3GPP networks), so a specifictraffic/flow is associated with only one of the two.

The aggregation of WLAN and 3GPP at a higher layer by employingmechanisms such as Multi-Path Transmission Control Protocol (MPTCP) hasbeen known for quite some time, while aggregation between the twonetworks at a lower layer is a rather new concept that is gaining a lotof momentum in the industry. A work item on tight WLAN aggregation hasbeen approved for 3GPP Long Term Evolution (LTE) Release 13 (Rel-13)[Intel Corporation et al., “RP-150510: New WI Proposal: LTE-WLAN RadioLevel Integration and Interworking Enhancement,” 3GPP TechnicalSpecification Group (TSG) Radio Access Network (RAN) Meeting #67, Mar.9-12, 2015, Shanghai, China], as described above in the Backgroundsection entitled “Tight Integration/Aggregation between 3GPP and WLAN.”In addition, 3GPP is already working on Licensed Assisted Access (LAA),as described above in the Background section entitled “CarrierAggregation (CA) and Licensed Assisted Access (LAA).”

It is assumed that a particular UE and a particular network willsimultaneously support multiple of the above solutions, or mechanisms,for integration/aggregation between 3GPP and WLAN as well as one or morefuture solutions for integration/aggregation between 3GPP and WLAN.Currently, there is no mechanism for the operator (and the network) tocontrol which of the solutions is selected for a particular subscriber(or subscriber group). Thus, new mechanisms are needed in order tocontrol which of the above solutions for 3GPP and WLANintegration/aggregation is to be used when combining traditional usageof 3GPP access with WLAN and/or unlicensed spectrum.

In order to address this issue, systems and methods are disclosed hereinthat enable a cellular network (e.g., a network node such as a basestation), and thus the network operator, to control which of thedifferent solutions, or mechanisms, for 3GPP and WLAN and/or unlicensedspectrum integration/aggregation is used for a particular subscriberand, thus, a particular UE. In some embodiments, a core network of acellular communications network provides an indication(s) of a preferredsolution(s) to a RAN (e.g., to a base station, which in 3GPP LTE, isreferred to as an enhanced or evolved Node B (eNB)). The indication(s)of the preferred solution(s) is, at least in some embodiments, providedfrom the core network to the RAN when a UE context for the UE is createdor modified in the RAN (e.g., during a UE attachment procedure). Theindication(s) is referred to herein as an Allowed WLAN/Unlicensed BandSolution(s) (AWUBS(s)).

In some embodiments, the AWUBS(s) of the preferred solution(s) is asingle AWUBS of a single preferred solution. In other embodiments, theAWUBS(s) of the preferred solution(s) includes multiple AWUBSs formultiple preferred solutions. In some embodiments, a priority, orpreference, order between the different preferred solutions may also beindicated. In other embodiments, a priority, or preference, orderbetween the different preferred solutions is not indicated. In someembodiments, the core network communicates the AWUBS(s) of the preferredsolution(s) to the RAN via an existing Information Element (IE) (e.g.,Subscriber Profile Identity (SPID) and/or Handover Restriction List(HRL)). In other embodiments, the core network communicates the AWUBS(s)of the preferred solution(s) to the RAN via a new IE.

In this regard, FIG. 10 illustrates a wireless system 10 that enablesintegration/aggregation of a cellular network 12 and a WLAN 14. In thedescription provided herein, the cellular network 12 is a 3GPP network(e.g., an LTE network) and, as such, 3GPP terminology is oftentimesused. However, the present disclosure is not limited thereto. As such,while 3GPP terminology is oftentimes used herein, it should beunderstood that these terms should be understood in their general sense(e.g., an eNB should be understood generally as a base station and a UEshould be understood generally as a wireless device) unless explicitlystated or otherwise required.

As illustrated, the cellular network 12 includes an Evolved UniversalTerrestrial RAN (EUTRAN) 16, which includes an eNB 18 (which may moregenerally be referred to herein as a base station). Note that while onlyone eNB 18 is illustrated for clarity and ease of discussion, the EUTRAN16 typically includes many eNBs 18. The cellular network 12 alsoincludes an Evolved Packet Core (EPC) 20, which includes a MobilityManagement Entity (MME) 22 communicatively coupled to the eNB 18 via anS1-MME interface, a Home Location Register (HLR)/Home Subscriber Server(HSS) 24 communicatively coupled to the MME 22 via an S6a interface, aServing Gateway (S-GW) 26 communicatively coupled to the eNB 18 via anS1-U interface, a Packet Data Network Gateway (P-GW) 28 communicativelycoupled to the S-GW 24 via an S5 interface, and a Policy and ChargingRules Function (PCRF) 30 communicatively coupled to the P-GW 28 via a Gxinterface. The operation and functionality of the MME 22, the HLR/HSS24, the S-GW 26, the P-GW 28, and the PCRF 30 are well-known to those ofordinary skill in the art and, as such, are not repeated herein. TheWLAN 14 includes an Access Point (AP) 32, but may also include AccessControllers (ACs), Gateways (GWs), etc. Notably, while in this examplethe eNB 18 and the AP 32 are not co-located, in some implementations theeNB 18 and the AP 32 may be co-located. Also note that the HLR/HSS 24may also be referred to herein (equivalently) as an HSS 24, where theHLR is a part of the HSS 24.

A UE 34 supports wireless communication with both the eNB 18 of thecellular network 12 and the AP 32 of the WLAN 14. Note that while onlyone UE 34 is illustrated, there may be many UEs 34. Further, thecellular network 12, the WLAN 14, and the UE 34 each support one or moresolutions for integration/aggregation of the cellular network 12 (e.g.,3GPP) and the WLAN 14 and/or unlicensed frequency spectrum. As notedabove, these solutions are referred to herein as AWUBSs. As an example,the possible values for the AWUBS indications and the correspondingAWUBSs may be or include:

-   -   AWUBS-1: LTE/WLAN interworking as defined in 3GPP Rel-12    -   AWUBS-2: LTE/WLAN interworking as defined in 3GPP Rel-13 (e.g.,        additional functionality added to LTE/WLAN interworking as        defined in 3GPP Rel-12 such as, for example, the addition of        WLAN measurement reporting over the LTE RRC protocol).    -   AWUBS-3: Tight LTE/WLAN aggregation as defined in 3GPP Rel-13    -   AWUBS-4: LAA as defined in 3GPP Rel-13    -   AWUBS-5: Future extension (e.g., LAA as defined in 3GPP Release        14 (Rel-14)).        Note that the AWUBSs and the corresponding values for the AWUBS        indication above are provided only as an example. Other AWUBSs        and corresponding values or the AWUBS indications may        additionally or alternatively be used.

The cellular network 12, the WLAN 14, and the UE 34 may supportdifferent sets of AWUBSs. Systems and methods are disclosed herein thatenable the cellular network 12 (and thus a network operator) to decidewhich AWUBS is used for the UE 34. In this regard, FIG. 11 illustratesthe operation of the wireless system 10 according to some embodiments ofthe present disclosure. In this embodiment, the AWUBS indication(s)is(are) provided to the eNB 18 from the EPC 20 during a procedure whenUE context is created or modified in the EUTRAN 16, but the presentdisclosure is not limited thereto. As illustrated, the UE 34 sends arequest to the eNB 18, where the request is to transition the UE 34 froman IDLE state to a CONNECTED state (e.g., from RRC_IDLE to RRC_CONNECTEDin LTE), in this example (step 100). The request may be, for example, an(initial) attach request, but is not limited thereto. The request may beany request made by the UE 34 to transition from the IDLE state or theCONNECTED state. In some embodiments, the request includes UE capabilityinformation, where the UE capability information may include, forexample, information that explicitly or implicitly indicates whichAWUBS(s) is(are) supported by the UE 34. The eNB 18 sends the request tothe EPC 20 (step 102). At this point, the UE 34, the eNB 18, and the EPC20 exchange conventional signaling related to the request (step 104).

Either after or sometime during the exchange of related signaling, as aresult of the request, the EPC 20 sends an AWUBS indication(s) to theeNB 18, where the AWUBS indication(s) is(are) indicative of an AWUBS(s)that is permitted to be used, or allowed, for the UE 34 (step 106). Insome embodiments, the AWUBS indication(s) is a single AWUBS indicationthat is indicative of a single AWUBS that is permitted to be used forthe UE 34. In other embodiments, the AWUBS indication(s) includesmultiple AWUBS indications that are indicative of multiple AWUBSs thatare permitted to be used for the UE 34. Further, in some embodiments,the EPC 20 also communicates relative priorities, or preferences, of themultiple AWUBSs. For example, the AWUBS indications may be provided in alist of AWUBS indications where the ordering of the list indicates therelative priorities of the corresponding AWUBSs. In other embodiments,the relative priorities, or preferences, of the multiple AWUBSs are notindicated by the EPC 20. As discussed below in detail, the AWUBSindication(s) (and, in some embodiments, the relative priorities of thecorresponding AWUBSs indicated by the AWUBS indication) may becommunicated from the EPC 20 to the eNB 18 using any suitable mechanismsuch as, but not limited to, a SPID, a HRL, and/or a new IE.

Optionally (i.e., in some embodiments), the eNB 18 selects the AWUBS tobe used for the UE 34 based on the AWUBS indication(s) received from theEPC 20 (step 108). This selection is particularly beneficial forembodiments in which multiple AWUBS indications are received from theeNB 18. In some embodiments, the eNB 18 selects the AWUBS to be usedbased on the AWUBS indication(s) and, possibly, the relative prioritiesof the corresponding AWUBSs and additional information such as, forexample, knowledge of which AWUBS(s) are supported by the EUTRAN 16(e.g., the eNB 18) and/or knowledge of which AWUBS(s) are supported bythe WLAN 14. Thus, for example, the eNB 18 may select the highestpriority AWUBS indicated by the AWUBS indication(s) received from theEPC 20 for the UE 34 that is also supported by the eNB 18 and the AP 32of the WLAN 14. Note, however, that if only one AWUBS indication isreceived from the EPC 20, then, in some embodiments, the selection step108 is not performed. In other words, the single AWUBS indicated by theEPC 20 may be automatically selected.

Lastly, the eNB 18 and the UE 34 use the (selected or indicated) AWUBS(step 110). With respect to step 110, dashed lines between the UE 34 andthe AP 32 and between the eNB 18 and the AP 32 indicate that, in some ofthe AWUBS solutions, the AP 32 is also impacted. Notably, the details ofhow the eNB 18 and the UE 34 use the AWUBS depend on the particularAWUBS. For example, if the (selected or indicated) AWUBS is 3GPP/WLANintegration according to 3GPP Rel-12, the eNB 18 may use the AWUBS bysending one or more assistance parameters to the UE 34, where the UE 34uses the assistance parameter(s) for access selection. As discussedabove, these assistance parameters may include thresholds, an OffloadingPreference Indicator (OPI), WLAN identifiers, and/or RAN rules/policies.As another example, if the (selected or indicated) AWUBS is 3GPP/WLANintegration according to 3GPP Rel-13, the eNB 18 may use the AWUBS byactivating and performing WLAN measurement reporting over the LTE RRCprotocol. As another example, if the (indicated or selected) AWUBS istight integration/aggregation according to 3GPP Rel-13, then the eNB 18may use the AWUBS by, for instance, providing Packet Data ConvergenceProtocol (PDCP), Radio Link Control (RLC), or Medium Access Control(MAC) 3GPP and WLAN integration/aggregation with respect to the UE 34.Further, the eNB 18 may use the AWUBS by, for example, configuring theWLAN AP 32 via an Xw interface, forward aggregated data to the WLAN AP32 via the Xw interface, etc. As yet another example, if the (indicatedor selected) AWUBS is LAA, then the eNB 18 may, for example, configure aSecondary Component Carrier (SCC) for the UE 34 in an unlicensedfrequency band according to a LAA scheme.

FIG. 12 illustrates the operation of the wireless system 10 in moredetail according to some embodiments of the present disclosure. FIG. 12is similar to FIG. 11, but provides further details regarding theinteraction between the eNB 18 and the EPC 20 according to someembodiments of the present disclosure. As illustrated, the UE 34 sends arequest to the eNB 18 to transition the UE 34 from the IDLE state to theCONNECTED state (step 200). The request may be, for example, an(initial) attach request, but is not limited thereto. The request may beany request made by the UE 34 to transition from the IDLE state or theCONNECTED state. In some embodiments, the request includes UE capabilityinformation, where the UE capability information may include, forexample, information that explicitly or implicitly indicates whichAWUBS(s) is(are) supported by the UE 34. The eNB 18 sends the request tothe MME 22 within the EPC 20 (step 202). At this point, the UE 34, theeNB 18, and the EPC 20 exchange conventional signaling related to therequest (step 204).

After the exchange of the signaling in step 204, as a result of therequest, the MME 22 retrieves subscription information for the UE 34 (orsubscriber) from the HLR/HSS 24 (step 206). The HLR/HSS 24 then sendssubscription information for the UE 34 to the MME 22, where thesubscription information includes an AWUBS indication(s) that is(are)indicative of an AWUBS(s) that is permitted to be used, or allowed, forthe UE 34 (step 208). As discussed above, in some embodiments, the AWUBSindication(s) is a single AWUBS indication that is indicative of asingle AWUBS that is permitted to be used for the UE 34. In otherembodiments, the AWUBS indication(s) includes multiple AWUBS indicationsthat are indicative of multiple AWUBSs that are permitted to be used forthe UE 34. Further, in some embodiments, the subscription informationalso communicates relative priorities, or preferences, of the multipleAWUBSs. For example, the AWUBS indications may be provided in a list ofAWUBS indications within the subscription information, where theordering of the list indicates the relative priorities of thecorresponding AWUBSs. In other embodiments, the relative priorities, orpreferences, of the multiple AWUBSs are not indicated.

After the MME 22 receives the subscription information for the UE 34,some additional signaling related to the request may be exchangedbetween the UE 34, the eNB 18, and the EPC 20 (step 210). The MME 22then sends a UE context related request (e.g., a UE context creationrequest (e.g., a S1AP initial context setup request in LTE) or a UEcontext modification request) to the eNB 18, where the UE contextrelated request includes the AWUBS indication(s) and, in someembodiments, the relative priorities of the indicated AWUBSs (step 212).Note that while step 212 is shown separately here, this signaling couldbe part of the signaling in step 210. In some embodiments, the AWUBSindication(s) are communicated in the UE context related request usingan SPID IE, a HRL IE, and/or a new IE.

As discussed above, optionally (i.e., in some embodiments), the eNB 18selects the AWUBS to be used for the UE 34 based on the AWUBSindication(s) received from the MME 22 (step 214). Again, this selectionis particularly beneficial for embodiments in which multiple AWUBSindications are received from the eNB 18. In some embodiments, the eNB18 selects the AWUBS to be used based on the AWUBS indication(s) and,possibly, the relative priorities of the corresponding AWUBSs andadditional information such as, for example, knowledge of which AWUBS(s)are supported by the EUTRAN 16 (e.g., the eNB 18) and/or knowledge ofwhich AWUBS(s) are supported by the WLAN 14. Note, however, that if onlyone AWUBS indication is received from the EPC 20, then, in someembodiments, the selection step 214 is not performed. In other words,the single AWUBS indicated by the EPC 20 may be automatically selected.Lastly, the eNB 18 and the UE 34 use the (selected or indicated) AWUBS(step 216). With respect to step 216, dashed lines between the UE 34 andthe AP 32 and between the eNB 18 and the AP 32 indicate that, in some ofthe AWUBS solutions, the AP 32 is also impacted.

FIG. 13 illustrates the operation of the wireless system 10 according tosome embodiments of the present disclosure. FIG. 13 is similar to FIG.12 but where there is only a single AWUBS indication. As illustrated,the UE 34 sends a request to the eNB 18 to transition the UE 34 from theIDLE state to the CONNECTED state (step 300). The request may be, forexample, an (initial) attach request, but is not limited thereto. Therequest may be any request made by the UE 34 to transition from the IDLEstate or the CONNECTED state. In some embodiments, the request includesUE capability information, where the UE capability information mayinclude, for example, information that explicitly or implicitlyindicates which AWUBS(s) is(are) supported by the UE 34. The eNB 18sends the request to the MME 22 within the EPC 20 (step 302). At thispoint, the UE 34, the eNB 18, and the EPC 20 exchange conventionalsignaling related to the request (step 304).

After the exchange of signaling related to the request in step 304, theMME 22 retrieves subscription information for the UE 34 (or subscriber)from the HLR/HSS 24 (step 306). The HLR/HSS 24 then sends subscriptioninformation for the UE 34 to the MME 22, where the subscriptioninformation includes a single AWUBS indication that is indicative of asingle AWUBS that is permitted to be used, or allowed, for the UE 34(step 308). After the MME 22 receives the subscription information forthe UE 34, some additional signaling related to the request may beexchanged between the UE 34, the eNB 18, and the EPC 20 (step 310). TheMME 22 then sends a UE context related request to the eNB 18, where theUE context related request includes the single AWUBS indication (step312). The UE context related request may be, for example, a UE contextcreation request or a UE context modification request.

In some embodiments, the AWUBS indication is communicated in the UEcontext related request as an SPID IE, a HRL IE, and/or a new IE. Withrespect to an SPID IE, the SPID IE is currently limited to 8 bits (i.e.,value range from 1 to 256). The number of total AWUBS solutions maylimit the different possibilities for the AWUBS indication. If the totalnumber of solutions is less than 4, then it is enough with 2 bits toindicate which of the solutions is permitted, or allowable, for the UE34. Similarly, if the number of solutions is 2, then 1 bit suffices;and, if the total number of solutions is 8 or less, then 3 bits willsuffice. Referring to the example above for AWUBS-1 through AWUBS-4,there are, in that example, 4 different solutions and, therefore, 2 bitsof the SPID are needed for the AWUBS indication. These 2 bits could beany of the 8 bits of the SPID.

In other embodiments, the AWUBS indication is communicated in the UEcontext related request as an HRL IE. The HRL is not space-limited inthe same sense as SPID and, in this case, the different values for theAWUBS indication can be indicated, for example, as illustrated in Table2 below. The principle described for HRL can also be used for any new IEinstead of the HRL IE.

TABLE 2 IE type and Semantics IE/Group Name Presence Range referencedescription Allowed O ENUMERATED WLAN/Unlicensed (AWUBS-1, BandSolutions AWUBS-2, AWUBS-3, AWUBS-4, AWUBS-5, . . .

As discussed above, optionally (i.e., in some embodiments), the eNB 18selects the AWUBS to be used for the UE 34 based on the AWUBSindication(s) received from the MME 22 (step 314). Here, since there isonly a single AWUBS indication, step 314 may not be performed. In otherwords, the single AWUBS indicated by the EPC 20 may be automaticallyselected. Lastly, the eNB 18 and the UE 34 use the (selected orindicated) AWUBS (step 316). With respect to step 316, dashed linesbetween the UE 34 and the AP 32 and between the eNB 18 and the AP 32indicate that, in some of the AWUBS solutions, the AP 32 is alsoimpacted.

FIG. 14 illustrates the operation of the wireless system 10 according tosome embodiments of the present disclosure. FIG. 14 is similar to FIG.12 but in FIG. 14 there are multiple AWUBS indications with explicit orimplicit priorities. As illustrated, the UE 34 sends a request to theeNB 18 to transition the UE 34 from the IDLE state to the CONNECTEDstate (step 400). The request may be, for example, an (initial) attachrequest, but is not limited thereto. The request may be any request madeby the UE 34 to transition from the IDLE state or the CONNECTED state.In some embodiments, the request includes UE capability information,where the UE capability information may include, for example,information that explicitly or implicitly indicates which AWUBS(s)is(are) supported by the UE 34. The eNB 18 sends the request to the MME22 within the EPC 20 (step 402). At this point, the UE 34, the eNB 18,and the EPC 20 exchange conventional signaling related to the request(step 404).

After the exchange of signaling in step 404, as a result of the request,the MME 22 retrieves subscription information for the UE 34 (orsubscriber) from the HLR/HSS 24 (step 406). The HLR/HSS 24 then sendssubscription information for the UE 34 to the MME 22, where thesubscription information includes AWUBS indications that are indicativeof multiple AWUBSs that are permitted to be used, or allowed, for the UE34 as well as indications of the relative priorities of the indicatedAWUBSs (step 408). The priorities of the indicated AWUBSs may beexplicitly indicated (e.g., via assigned priority values) or implicitlyindicated (e.g., via ordering in a list of AWUBS indications). After theMME 22 receives the subscription information for the UE 34, someadditional signaling related to the request may be exchanged between theUE 34, the eNB 18, and the EPC 20 (step 410). The MME 22 then sends a UEcontext related request to the eNB 18, where the UE context relatedrequest includes the AWUBSs indications as well as indications of theirrelative priorities (step 412). The UE context related request may be,for example, a UE context creation request or a UE context modificationrequest.

In some embodiments, the AWUBS indications are communicated in the S1APinitial context setup request as an SPID, a HRL, and/or a new IE. Withrespect to a HRL, the AWUBS indications are, in some embodiments, storedin the HRL as an enumerator, where each entry is associated with aparticular priority. The priority could be implicitly or explicitlyindicated. In the former case, the list is constructed in such a way sothat the first entry has the highest priority, the second entry has thesecond highest priority, and so on. In the latter case, each entry has aparticular priority associated to it (e.g., expressed in a numericalvalue). In some embodiments, a certain reserved priority value (e.g.,the lowest or highest in the set of possible values, e.g., “0” of “255”in an 8 bit field) could indicate that the particular solution is notallowed for this subscriber/UE 34.

With respect to an SPID, since the SPID is currently limited to 8 bits,a bitmap needs to be created for the different solutions in priorityorder. As an example, the last 6 bits of the SPID could be used toindicate the set of allowed solutions (i.e., AWUBS-1 through AWUBS-4,both included). In this case, a mapping is defined based on number ofallowed solutions and their respective priorities. For instance, if theset of possible solutions is a set of 4 solutions {AWUBS-1, AWUBS-2,AWUBS-3, AWUBS-4}, then there are 64 different permutations of the set.The number of combinations in the set can be computed as:

₄ P ₄+₄ P ₃+₄ P ₂+₄ P ₁=64.

Then, the 64 different combinations can be expressed with the 6 bits inthe SPID (using a decimal to binary mapping). In some embodiments, atable that defines mappings between the different decimal (or bit binarybit) values and the different permutations of allowed, or permitted,solutions is predefined (e.g., by standard). One example of such a tableis given below in Table 3. However, this is only an example.

TABLE 3 Decimal Value Allowed Solutions in Order of Priority 1 AWUBS-1 2AWUBS-2 3 AWUBS-3 4 AWUBS-4 5 AWUBS-1, AWUBS-2 6 AWUBS-1, AWUBS-3 [. ..] [. . .] 61 AWUBS-1, AWUBS-3, AWUBS-4, AWUBS-2 62 AWUBS-1, AWUBS-3,AWUBS-2, AWUBS-4 63 AWUBS-1, AWUBS-2, AWUBS-4, AWUBS-3 64 AWUBS-1,AWUBS-2, AWUBS-3, AWUBS-4

Another option is to extend the SPID to more bits so that futuresolutions could be also included. Yet another option is to create a newIE, which could provide a prioritized list of the different solutions.

In some embodiments, the relative priorities of the different solutionsare UE-specific. However, in other embodiments, the relative prioritiesof the different solutions are universal for all UEs 34. This universalprioritization of the different solutions may be defined by, e.g., thenetwork operator. In embodiments where the relative priorities of thedifferent solutions are universal, then the AWUBS indications (e.g., asrepresented by the bits of the SPID) will only indicate the permittedsolutions for the UE 34 without any specific ordering. The relativepriorities of the permitted solutions will then be known by the eNB 18based on the predefined priorities of the different solutions. Thus, insome embodiments, the number of bits required in the SP ID will be equalto the amount of available solutions, where each bit signifies thesupport of that solution for that UE 34 or not. The predefined priorityorder can be configured in the EUTRAN 16 using Operations and Management(O&M) functionality, or could be signaled from the EPC 20 to the EUTRAN16 when the EPC-EUTRAN interface is established (for example, the S1-MMEinterface in the case of EPC and EUTRAN/LTE).

A compromise between per SPID prioritization or universal prioritizationthat is applicable to all UEs 34 is to define priority classes. Morespecifically, different prioritizations of the solutions are defined formultiple priority classes, and the SPID including the AWUBS indicationsis associated with one of the priority classes. For example, an operatorcan define 4 classes as: Class 1: AWUBS-1>AWUBS-2>AWUBS-3>AWUBS-4; Class2: AWUBS-1>AWUBS-2>AWUBS-4>AWUBS-3; Class 3:AWUBS-1>AWUBS-2>AWUBS-4>AWUBS-3; and Class 4:AWUBS-4>AWUBS-3>AWUBS-2>AWUBS-1). These four classes can be defined by 2bits. Thus, in some embodiments, the SPID includes a first set of bitsthat define the priority class (e.g., 2 bits for indicating one of 4priority classes) and a set of bits that provide the AWUBS indications(e.g., 1 bit for each possible solution, where “1” indicates that thesolution is permitted and “0” indicates that the solution is notpermitted).

Neither the HRL nor a new IE are space-limited and in this case thedifferent values can be indicated, for example, as following:

TABLE 4 IE/Group IE type and Semantics Name Presence Range referencedescription AWUBS 1 with Priority List >AWUBS 1 . . . maxnoofAWUBS with<maxnoofAWUBS> defined Priority in standard Item lEs in an extendableway >>AWUBS M ENUMERATED (AWUBS-1, AWUBS-2, AWUBS-3, AWUBS-4, AWUBS-5, .. . >>>AWUBS M ENUMERATED(1, 2, Priority 3, 4, 5, . . .)

As discussed above, the eNB 18 selects the AWUBS to be used for the UE34 based on the AWUBS indications and the priorities of thecorresponding AWUBS received from the MME 22 (step 414). For example,assume that the UE 34 supports AWUBS-1 (LTE/WLAN interworking as definedin 3GPP Rel-12), AWUBS-3 (tight LTE/WLAN aggregation as defined in 3GPPRel-13), and AWUBS-4 (LAA as defined in 3GPP Rel-13) and the eNB 18 andthe WLAN 14 support AWUBS-3 and AWUBS-4. Further, for this example,assume that the HLR/HSS 24 is configured with the following AWUBSpriority list for the UE 34: {AWUBS-1, AWUBS-4, AWUBS-3}. In thisexample, the eNB 18 selects AWUBS-4 since AWUBS-4 is the highestpriority AWUBS listed in the AWUBS priority list for the UE 34 that isalso supported by the UE 34, the eNB 18, and the WLAN 14. Lastly, theeNB 18 and the UE 34 use the selected AWUBS (step 416). With respect tostep 416, dashed lines between the UE 34 and the AP 32 and between theeNB 18 and the AP 32 indicate that, in some of the AWUBS solutions, theAP 32 is also impacted.

FIG. 15 illustrates the operation of the wireless system 10 according tosome embodiments of the present disclosure. FIG. 15 is similar to FIG.14 but where there are no priority indications for the permitted AWUBSs.As illustrated, the UE 34 sends a request including UE capabilityinformation to the eNB 18 (step 500). The UE capability information mayinclude, for example, information that explicitly or implicitlyindicates which AWUBS(s) is(are) supported by the UE 34. The eNB 18sends the request to the MME 22 within the EPC 20 (step 502). At thispoint, the UE 32, the eNB 18, and the EPC 20 exchange conventionalrelated signaling (step 504).

After the exchange of related signaling in step 504, the MME 22retrieves subscription information for the UE 34 (or subscriber) fromthe HLR/HSS 24 (step 506). The HLR/HSS 24 then sends subscriptioninformation for the UE 34 to the MME 22, where the subscriptioninformation includes AWUBS indications that are indicative of multipleAWUBSs that are permitted to be used for the UE 34 without anyindication (explicit or implicit) of priorities (step 508). After theMME 22 receives the subscription information for the UE 34, someadditional related signaling may be exchanged between the UE 34, the eNB18, and the EPC 20 (step 510). The MME 22 then sends a UE contextrelated request to the eNB 18, where the UE context related requestincludes the AWUBS indications (step 512).

In some embodiments, the AWUBS indications are communicated in the S1APinitial context setup request as an SPID, a HRL, and/or a new IE. Withrespect to the SPID, since the SPID is currently limited to 8 bits, eachallowed solution can be allocated a particular bit. If the bit assignedto a particular solution is set to “0,” then the solution is notpermitted for the UE 34. Conversely, if the bit is set to “1,” then thesolution is permitted for the UE 34. Looking again at the example abovewhere there are 4 possible solutions (AWUBS-1 through AWUBS-4), then 4bits are used to indicate whether each of those solutions is permittedfor the UE 34 or not. An example of the SPID mapping for 4 arbitrarybits (e.g., first 4 bits) of the SPID is shown below in Table 5.

TABLE 5 Allowed/ Solution Number Not Allowed Bit 1: AWUBS-1 1 Bit 2:AWUBS-2 0 Bit 3: AWUBS-3 0 Bit 4: AWUBS-4 1

In some embodiments, the mapping of AWUBSs to SPID bits is predefined(e.g., standardized).

Neither the HRL nor the new IE are space-limited and this case thedifferent values can be indicated, for example, as shown in Table 6below.

TABLE 6 lE/Group IE type and Semantics Name Presence Range referencedescription AWUBS 1 List >AWUBS 1 . . . maxnoofAWUBS Item <maxnoofAWUBS>defined IEs in standard in an extendable way >>AWUBS M ENUMERATED(AWUBS-1, AWUBS-2, AWUBS-3, AWUBS-4, AWUBS-5, . . .

As discussed above, the eNB 18 selects the AWUBS to be used for the UE34 based on the AWUBS indications received from the MME 22 (step 514).For example, assume that the UE 34 supports AWUBS-1 (LTE/WLANinterworking as defined in 3GPP Rel-12), AWUBS-3 (tight LTE/WLANaggregation as defined in 3GPP Rel-13), and AWUBS-4 (LAA as defined in3GPP Rel-13) and the eNB 18 and the WLAN 14 support AWUBS-3 and AWUBS-4.Further, for this example, assume that the HLR/HSS 24 is configured withthe following AWUBS list for the UE 34: {AWUBS-1, AWUBS-4, AWUBS-3}. Inthis example, the eNB 18 selects either AWUBS-3 or AWUBS-4 since bothAWUBS-3 and AWUBS-4 are permitted for the UE 34 (per the AWUBSlist/indications) and are supported by the UE 34, the eNB 18, and theWLAN 14. Notably, the eNB 18 may utilize additional information toselect between AWUBS-3 and AWUBS-4 or may select either AWUBS-3 orAWUBS-4 using a desired selection technique (e.g., random selection).Lastly, the eNB 18 and the UE 34 use the selected AWUBS (step 516). Withrespect to step 516, dashed lines between the UE 34 and the AP 32 andbetween the eNB 18 and the AP 32 indicate that, in some of the AWUBSsolutions, the AP 32 is also impacted.

FIG. 16 is a block diagram of the eNB 18 according to some embodimentsof the present disclosure. As illustrated, the eNB 18 includes abaseband unit 36 including one or more processors 38 (e.g., CentralProcessing Unit(s) (CPU(s)), Application Specific Integrated Circuit(s)(ASIC(s)), Field Programmable Gate Array(s) (FPGA(s)), or the like),memory 40, and a network interface 42 communicatively coupling the eNB18 to, e.g., the EPC 20. The eNB 18 also includes one or more radiounits 44 including transmitter(s) 46 and receiver(s) 48 connected toantennas 50. In some embodiments, the functionality of the eNB 18described herein is implemented in software that is stored in the memory40 and executed by the processor(s) 38.

In some embodiments, a computer program including instructions which,when executed by at least one processor, causes the at least oneprocessor to carry out the functionality of the eNB 18 according to anyof the embodiments described herein is provided. In some embodiments, acarrier containing the aforementioned computer program product isprovided. The carrier is one of an electronic signal, an optical signal,a radio signal, or a computer readable storage medium (e.g., anon-transitory computer readable medium such as the memory 40).

FIG. 17 is a block diagram of the eNB 18 according to some otherembodiments of the present disclosure. As illustrated, the eNB 18includes an AWUBS indication(s) reception module 52, an AWUBS selectionmodule 54, and an AWUBS use module 56, each of which is implemented insoftware. The AWUBS indication(s) reception module 52 operates to obtainone or more AWUBS indications from the EPC 20 for the UE 34, asdescribed above. The AWUBS selection module 54 operates to select anAWUBS to use for the UE 34 based on the AWUBS indication(s) receivedfrom the EPC 20, as described above. The AWUBS use module 56 operates,together with the UE 34, to use the selected (or indicated) AWUBS, asdescribed above.

FIG. 18 is a block diagram of a core network node 58 according to someembodiments of the present disclosure. The core network node 58 is, forexample, the MME 22 or the HLR/HSS 24. As illustrated, the core networknode 58 includes one or more processors 60 (e.g., CPU(s), ASIC(s),FPGA(s), or the like), memory 62, and a network interface 64communicatively coupling the core network node 58 to, e.g., other nodesin the EPC 20 and the EUTRAN 16. In some embodiments, the functionalityof the core network node 58 described herein is implemented in softwarethat is stored in the memory 62 and executed by the processor(s) 60.

In some embodiments, a computer program including instructions which,when executed by at least one processor, causes the at least oneprocessor to carry out the functionality of the core network node 58(e.g., the MME 22 or the HLR/HSS 24) according to any of the embodimentsdescribed herein is provided. In some embodiments, a carrier containingthe aforementioned computer program product is provided. The carrier isone of an electronic signal, an optical signal, a radio signal, or acomputer readable storage medium (e.g., a non-transitory computerreadable medium such as the memory 62).

FIG. 19 illustrates the MME 22 according to some embodiments of thepresent disclosure. As illustrated, the MME 22 includes an AWUBSindication(s) obtaining module 66 and an AWUBS indication(s) sendingmodule 68, each of which is implemented in software. The AWUBSindication(s) obtaining module 66 operates to obtain (via an appropriatenetwork interface of the MME 22, not shown) subscription informationcontaining one or more AWUBS indications for the UE 34, as describedabove. The AWUBS indication(s) sending module 68 operates to send (viaan appropriate network interface of the MME 22, not shown) the AWUBSindication(s) for the UE 34 to the eNB 18, as described above.

FIG. 20 illustrates the HLR/HSS 24 according to some embodiments of thepresent disclosure. As illustrated, the HLR/HSS 24 includes a receptionmodule 70 and a sending module 72, each of which is implemented insoftware. The reception module 70 operates to receive a request (via anappropriate network interface of the HLR/HSS 24, not shown) from the MME22 for subscription information for the UE 34, as described above. Inresponse, the sending module 72 sends (via an appropriate networkinterface of the HLR/HSS 24, not shown) subscription informationcontaining one or more AWUBS indications for the UE 34 to the MME 22, asdescribed above.

Embodiments described herein enable the aggregation of a given user'straffic between WLAN and 3GPP networks. Furthermore, the differentiationbetween different subscribers or subscribers classes can be enhanced (ahigher differentiation granularity can be achieved based on the types ofallowed/enabled aggregation/integration solutions).

The following acronyms are used throughout this disclosure.

3GPP Third Generation Partnership Project AC Access Controller ANDSFAccess Network Discovery and Selection Function AP Access Point ASICApplication Specific Integrated Circuit AWUBS Allowed Wireless LocalArea Network/Unlicensed Band Solution CA Carrier Aggregation CCComponent Carrier CM Connection Manager CPU Central Processing Unit DUDigital Unit Ec/No Energy per Chip/spectral Noise density eNB Enhancedor Evolved Node B EPC Evolved Packet Core EUTRAN Evolved UniversalTerrestrial Radio Access Network FPGA Field Programmable Gate Array GSMGlobal System for Mobile Communications GW Gateway HLR Home LocationRegister HRL Handover Restriction List HSS Home Subscriber Server IDIdentifier IE Information Element IMSI International Mobile SubscriberIdentity IP Internet Protocol LAA License Assisted Access LLC LogicalLink Control LTE Long Term Evolution MAC Medium Access Control MHzMegahertz MME Mobility Management Entity MPTCP MultiPath TransmissionControl Protocol O&M Operations and Management OPI Offloading PreferenceIndicator OS Operation System PCC Primary Component Carrier PCellPrimary Serving Cell PCRF Policy and Charging Rules Function PDCP PacketData Convergence Protocol P-GW Packet Data Network Gateway PLMN PublicLand Mobile Network RAN Radio Access Network RAT Radio Access TechnologyRCPI Received Channel Power Indicator Rel-8 Release 8 Rel-10 Release 10Rel-12 Release 12 Rel-13 Release 13 Rel-14 Release 14 RF Radio FrequencyRFSP Radio Access Technology/Frequency Selection Priority RLC Radio LinkControl RRC Radio Resource Control RSCP Received Signal Code Power RSRPReference Signal Received Power RSRQ Reference Signal Received QualityRSSI Received Signal Strength Indication SCC Secondary Component CarrierSCell Secondary Serving Cell SCG Secondary Cell Group S-GW ServingGateway SI Study Item SPID Subscriber Profile Identity TCP TransmissionControl Protocol TR Technical Report TS Technical Specification TSGTechnical Specification Group UE User Equipment UMTS Universal MobileTelecommunications System VoIP Voice over Internet Protocol WCDMAWideband Code Division Multiple Access WFA Wi-Fi Alliance WLAN WirelessLocal Area Network

Those skilled in the art will recognize improvements and modificationsto the embodiments of the present disclosure. All such improvements andmodifications are considered within the scope of the concepts disclosedherein and the claims that follow.

What is claimed is:
 1. A method of operation of a Mobility ManagementEntity (MME) of a cellular communications network, the methodcomprising: obtaining subscription information for a User Equipment(UE), wherein the subscription information comprises one or more AllowedWireless Local Area Network/Unlicensed Band Solution (AWUBS) indicationsthat are indicative of one or more AWUBSs that are allowed for the UE;and sending a UE context related request to a base station in a radioaccess network of the cellular communications network, the UE contextrelated request comprising one of the one or more AWUBS indications. 2.The method of claim 1, wherein the one or more AWUBS indications consistof a single AWUBS indication that is indicative of a single AWUBS thatis allowed for the UE.
 3. The method of claim 1, wherein the one or moreAWUBS indications comprise a plurality of AWUBS indications that areindicative of a plurality of AWUBSs that are allowed for the UE.
 4. Themethod of claim 1, wherein the subscription information comprises a listof AWUBS indications consisting of the one or more AWUBS indications,and wherein an ordering of the one or more AWUBS indications within thelist of AWUBS indications is indicative of relative priorities of theone or more AWUBS indications.
 5. The method of claim 4, wherein therelative priorities of the one or more AWUBS indications are UEspecific.
 6. The method of claim 4, wherein the relative priorities ofthe one or more AWUBS indications are universal for the cellularcommunications network.
 7. The method of claim 1, wherein thesubscription information comprises a list of AWUBS indicationsconsisting of the one or more AWUBS indications without priorities. 8.The method of claim 1, wherein the UE context related request comprisesa Subscriber Profile Identity (SPID) information element associated withthe UE that comprises the one or more AWUBS indications.
 9. The methodof claim 1, wherein the UE context related request comprises a HandoverRestriction List (HRL) information element associated with the UE thatcomprises the one or more AWUBS indications.
 10. The method of claim 1,wherein the UE context related request comprises an information elementassociated with the UE that comprises the one or more AWUBS indications.11. The method of claim 1, wherein obtaining the subscriptioninformation for the UE comprises obtaining the subscription informationfor the UE from a Home Location Register (HLR)/Home Subscriber Server(HSS) of the cellular communications network.
 12. The method of claim 1,wherein the one or more AWUBSs that are allowed for the UE are preferredsolutions for providing internetworking between a wireless local areanetwork (WLAN) and the cellular communications network, and whereinsending the UE context related request comprises sending the UE contextrelated request comprising the one or more AWUBSs of the preferredsolutions to the base station via an information element.
 13. A MobilityManagement Entity (MME) of a cellular communications network, the MMEcomprising: a network interface communicatively coupling the MME toother network nodes of the cellular communications network; one or moreprocessors; and memory containing instructions executable by the one ormore processors, wherein the MME is operable to: obtain subscriptioninformation for a User Equipment (UE), wherein the subscriptioninformation comprises one or more Allowed Wireless Local AreaNetwork/Unlicensed Band Solution (AWUBS) indications that are indicativeof one or more AWUBSs that are allowed for the UE; and send a UE contextrelated request to a base station in a radio access network of thecellular communications network, the UE context related requestcomprising one of the one or more AWUBS indications.
 14. The MME ofclaim 13, wherein the MME is operable to obtain the subscriptioninformation for the UE in response to a request received from the basestation.
 15. The MME of claim 14, wherein the request comprises UEcapability information, and wherein the UE capability informationcomprises information that indicates which AWUBSs are supported by theUE.
 16. The MME of claim 14, wherein the request comprises a request totransition the UE from an idle state to a connected state.
 17. The MMEof claim 13, wherein the UE context related request comprises aSubscriber Profile Identity (SPID) information element associated withthe UE that comprises the one or more AWUBS indications.
 18. The MME ofclaim 13, wherein the UE context related request comprises a HandoverRestriction List (HRL) information element associated with the UE thatcomprises the one or more AWUBS indications.
 19. The MME of claim 13,wherein the MME is operable to obtain the subscription information forthe UE when a UE context is modified for the UE in the radio accessnetwork of the cellular communications network.
 20. The MME of claim 13,wherein the one or more AWUBSs that are allowed for the UE are preferredsolutions for providing internetworking between a wireless local areanetwork (WLAN) and the cellular communications network, and wherein theMME is operable to send the UE context related request comprising theone or more AWUBSs of the preferred solutions to the base station via aninformation element.